-
Notifications
You must be signed in to change notification settings - Fork 7
Do not reuse PersistentContextPtr instances #261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Overall package sizeSelf size: 1.77 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | source-map | 0.7.6 | 185.63 kB | 185.63 kB | | pprof-format | 2.2.1 | 163.06 kB | 163.06 kB | | p-limit | 3.1.0 | 7.75 kB | 13.78 kB | | delay | 5.0.0 | 11.17 kB | 11.17 kB | | node-gyp-build | 3.9.0 | 8.81 kB | 8.81 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
ee05b8d to
42bb2d4
Compare
42bb2d4 to
e9cd659
Compare
e9cd659 to
f1af6c9
Compare
BridgeAR
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we can try this, I do not believe this is the actual cause of the report
|
@BridgeAR Actually I think it's good to remove Note: I see that |
What does this PR do?:
Removes caching/reuse of PersistentContextPtr instances.
Motivation:
This was always a speculative attempt to reduce native memory fragmentation. The standard library can be expected to do some of this itself, so we should not be doing this, especially since it is also removed in #255 and it seems to be causing issues (see #7355).
Additional Notes:
#255 also contains this, but we can roll it out as a quicker measure to try to eliminate the memory issue. An advantage of rolling this out separately is that #255 requires some changes in dd-trace-js too, while this as a standalone change does not.